-
Notifications
You must be signed in to change notification settings - Fork 0
Better exception management for Azure ServiceBus #1131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@mauroservienti made some more tweaks to the output, can you take a final look? |
mauroservienti
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor tweak; otherwise, looks good
|
|
||
| if (metricQueryResult is null) | ||
| { | ||
| throw new Exception("No metrics query results returned for Microsoft.ServiceBus/Namespace"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| throw new Exception("No metrics query results returned for Microsoft.ServiceBus/Namespace"); | |
| throw new Exception($"No metrics query results returned for {MicrosoftServicebusNamespacesMetricsNamespace}"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops, I had it to automerge, will apply it to master
This PR makes the code more picky about the results from the metrics API and also throws if the API call indicates an error